Method and apparatus for communicating between communication devices

ABSTRACT

Aspects of the subject disclosure may include, for example, receiving from a web real-time communications gateway a first request for communication services from a network resource, where the network resource does not utilize a web real-time communications protocol and where the first request is compliant with a markup language that differs from the web real-time communications protocol, directing the network resource to provide the communication services identified in the first request, receiving a first message from the web real-time communications gateway, where the first message is compliant with the markup language, translating the first message to a first updated message conforming to a protocol used by the network resource, where protocol differs from the markup language used for communicating with the web real-time communications gateway, and transmitting the updated first message to the network resource facilitating the communication services identified in the first request. Other embodiments are disclosed.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and apparatus forcommunicating between communication devices.

BACKGROUND

Web Real-Time Communications (WebRTC) is an application programminginterface (API) definition being developed by the World Wide WebConsortium (W3C) and a companion RTCWEB Internet Engineering Task Force(IETF) group to enable runtime platform-independent browser-to-browserapplications supporting voice calling, video chat, and peer-to-peer(P2P) file sharing without the need for plugins.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a system;

FIG. 2 depicts an illustrative embodiment of application programminginterfaces used in parts of the system of FIG. 1;

FIG. 3 depicts an illustrative embodiment of a method used by the systemdescribed in FIG. 1;

FIGS. 4-5 depict illustrative embodiments of communication systems thatprovide media services configured according to the method of FIG. 3;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1 and 4-5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments of a service translation system to reduce the complexity ofdeploying a WebRTC gateway that interacts with legacy network resourcesof a communication system. Other embodiments are included in the subjectdisclosure.

One embodiment of the subject disclosure includes a method forreceiving, by a web real-time communications gateway comprising aprocessor, a first request from a mobile communication deviceidentifying communication services requested from a network resourcethat does not utilize a web real-time communications protocol used bythe web real-time communications gateway, where the first request iscompliant with the web real-time communications protocol, generating, bythe web real-time communications gateway, a second request comprising amarkup language that differs from the web real-time communicationsprotocol, where the markup language is used by a service translationgateway that interfaces the web real-time communications gateway to aplurality of network resources that do not conform to the web real-timecommunications protocol, and where the plurality of network resourcesincludes the network resource identified in the first request,transmitting, by the web real-time communications gateway, the secondrequest to the service translation gateway to cause the servicetranslation gateway to facilitate the communication services of thenetwork resource identified in the first request, receiving, by the webreal-time communications gateway, a first message from the mobilecommunication device, where the first message is compliant with the webreal-time communications protocol used by the web real-timecommunications gateway, translating, by the web real-time communicationsgateway, the first message to a first updated message conforming to themarkup language used by the service translation gateway, andtransmitting, by the web real-time communications gateway, the updatedfirst message to the service translation gateway for delivery to thenetwork resource facilitating the communication services identified inthe first request.

One embodiment of the subject disclosure includes a machine-readablestorage medium having executable instructions. Execution of theinstructions by a processor, can cause the processor to performoperations including receiving a first request from a communicationdevice requesting communication services from a network resource thatdoes not utilize a web real-time communications protocol, where thefirst request is compliant with the web real-time communicationsprotocol, generating a second request comprising a markup language thatdiffers from the web real-time communications protocol, where the markuplanguage is used by a service translation gateway that interfaces to aplurality of network resources that do not utilize the web real-timecommunications protocol, and where the plurality of network resourcesincludes the network resource identified in the first request,transmitting the second request to the service translation gateway tofacilitate the communication services of the network resource identifiedin the first request, receiving a first message from the communicationdevice, where the first message is compliant with the web real-timecommunications protocol, translating the first message to a firstupdated message conforming to the markup language used by the servicetranslation gateway, and transmitting the updated first message to theservice translation gateway for delivery to the network resourcefacilitating the communication services identified in the first request.

One embodiment of the subject disclosure includes a service translationgateway having a memory to store executable instructions, and aprocessor coupled to the memory. Execution of the instructions by theprocessor can cause the processor to perform operations includingreceiving from a web real-time communications gateway a first requestfor communication services from a network resource, where thecommunication services are requested by a communication devicecommunicatively coupled to the web real-time communications gateway,where the network resource does not utilize a web real-timecommunications protocol used by the web real-time communicationsgateway, and where the first request is compliant with a markup languagethat differs from the web real-time communications protocol, directingthe network resource to provide the communication services identified inthe first request, receiving a first message from the web real-timecommunications gateway, where the first message is compliant with themarkup language, translating the first message to a first updatedmessage conforming to a protocol used by the network resource, whereprotocol differs from the markup language used for communicating withthe web real-time communications gateway, and transmitting the updatedfirst message to the network resource facilitating the communicationservices identified in the first request.

FIG. 1 depicts an illustrative embodiment of a system 100. System 100can comprise a WebRTC gateway 104 providing services to user equipment(UE) 102 executing WebRTC compliant applications. The WebRTC gateway 104can be a server or another suitable computing device executing softwarethat mimics in whole or in part the WebRTC standard or protocolpromulgated by the world wide web consortium (W3C), an internetengineering task force (IETF) group, or a combination of the two. UE 102shown in FIG. 1 can represent smart phones, laptop computers, tablets,desktop computers, or any other suitable computing device withcommunication resources. WebRTC compliant applications can be a webbrowser that utilizes software programs (e.g., Javascripts) that mimicthe WebRTC application program interface (API) specifications defined bythe WebRTC standard or protocol. Assisted by the WebRTC gateway 104,WebRTC browsers can support runtime platform-independentbrowser-to-browser applications such as voice calls, video chat, andpeer-to-peer (P2P) file sharing without the need for plugins. As shownin FIG. 1, WebRTC compliant UE 102 communicates with a WebRTC serverusing a WebRTC compliant protocol.

There are many legacy network resources 108 of a communication system(such as a cellular telephony system) that are not WebRTC compliant. Forexample, there are many short message service (SMS) servers andmultimedia messaging service (MMS) servers deployed throughout cellularsystems around the world that provide communication services to a largecommunity of UEs 102 which may not be WebRTC compliant. It isconceivable that legacy network resources 108 such as SMS and MMSservers can be upgraded to support a WebRTC protocol. However, it wouldbe too costly to upgrade such systems, especially if some of thesesystems were to be replaced or phased out over time. Similarly, it isconceivable that a WebRTC gateway 104 can be configured with all knownproprietary interfaces of legacy network resources 108. However,developing a universal interface that supports all proprietaryinterfaces would likely be commercially unviable and would likely delaythe deployment of WebRTC services.

To overcome these challenges, a service translation gateway 106 can beused that provides a common interface to the WebRTC gateway 104utilizing a markup language that provides access to all legacy networkresources 108. More than one service translation gateway 106 can be usedto support different clusters of legacy network resources 108.Accordingly, it is not necessary for a single model of a serviceprovider of service translation gateways 106 to supports all proprietaryinterfaces. The only requirement for all models of the servicetranslation gateways 106 is to provide a common communications interfaceto the WebRTC gateway 104 by way of a predefined markup language thatenables the WebRTC to request services from any legacy non-WebRTCcompliant network resource without requiring the WebRTC gateway 104 todirectly communicate with the legacy network resources 108. The servicetranslation gateway 106 can thus eliminate the need for the WebRTCgateway 104 to communicate over the proprietary interfaces or protocolsof the network resources 108, thereby simplifying the deployment ofWebRTC gateways 104. As the demand for WebRTC compliant devices grows,various models of service translation gateways 106 can be deployed tosupport different legacy network resources 106.

FIG. 2 depicts an illustrative embodiment of high-level and low-levellanguage application programming interfaces (APIs) which can be used inthe markup language utilized by the WebRTC gateway 104 and the servicetranslation gateway 106. The high-level language API (HLLAPI) canprovide a system-independent WebRTC gateway 104 a Meta-API structuredprogramming interface runtime environment to accelerate and improve theperformance of service translation gateways 106, thereby improvingthroughput across a plurality of heterogeneous, distributed WebRTCgateways 104 and network application processing environments of theservice translation gateways 106.

The purpose of a Low-Level Application Programming Interface (LLAPI) isto provide a plurality of WebRTC gateways 104 and service translationgateways 106 processing environment-dependent structured programminginterfaces which—in concert with the HLLAPI and Meta-API, and the markuplanguage used between the WebRTC gateways 104 and service translationgateways 106—accelerate and improve the computing platform performanceand throughput of WebRTC gateways 104 and service translation gateways106 across a plurality of heterogeneous, distributed processingplatforms and runtime environments.

The markup language can provide the WebRTC gateway 104 and the servicetranslation gateway 106 a dataset and file markup language forstructuring and presenting WebRTC content for use within a plurality ofproprietary standalone network application environments, and a pluralityof heterogeneous, distributed network application environments, WorldWide Web and Internet processing environments, Intranet processingenvironments, and Extranet processing environments.

FIG. 3 depicts an illustrative embodiment of a method 300 used by thesystem 100 of FIG. 1. Method 100 can begin with step 302 where theWebRTC gateway 104 receives a service request from UE1 for legacyservices of a specific network resource 108 to engage in communicationswith another UE2. The legacy services can be, for example, a user of UE1trying to send an SMS message to another user of UE2. At step 304, theWebRTC gateway 104 can transmit a markup language request to the servicetranslation gateway 106. The markup language request can identify aspecific legacy network resource 108 that is be requested by UE1. Instep 306, the service translation gateway 106 can in turn process themarkup language request and facilitate communications with the requestedlegacy network resource 108 according to the communication protocol usedby the network resource 108.

At step 308, the service translation gateway 106 can inform the WebRTCgateway 104 using the markup language described earlier that the networkresource 108 is ready. At step 310, the WebRTC gateway can inform UE1using the WebRTC protocol that that the network resource 108 is ready.UE1 at step 312 can initiate a message directed to UE2. The WebRTCgateway 104 receives the message from UE1 at step 314 using the WebRTCprotocol, and translates the message at step 316 using the markuplanguage and delivers it to the service translation gateway 106. Theservice translation gateway 106 in turn extracts the UE1 message fromthe markup language and delivers the UE1 message to the network resource108 in the non-WebRTC protocol of the network resource 108 in step 318.At step 320, the network resource 108 delivers the UE1 message to UE2utilizing the messaging protocol used by that system (e.g., SMS or MMSprotocols, or other protocols of other messaging services).

The foregoing process can be applied also in the reverse. For example,at step 322 the user of UE2 can send a response message to the networkresource 108 in the messaging protocol used by the network resource 108.At step 324 the network resource 108 can provide the UE2 message to theservice translation gateway 106 over its proprietary interface. At step326, the service translation gateway 106 can insert the UE2 message intothe markup language and deliver it to the WebRTC gateway 104. The WebRTCgateway 104 can in turn extract the UE2 message from the markup languageand deliver the UE2 message at step 330 to UE1 using the WebRTCprotocol.

The foregoing embodiments substantially reduce the complexity and costof deploying WebRTC gateways 104 and related WebRTC applications byproviding WebRTC gateways 104 a common or unified communicationsinterface to request services from legacy network resources 108 by wayof the service translation gateway 105, which shields the WebRTCgateways 104 from the many legacy network resource protocols andproprietary interfaces presently in use, thereby enabling rapiddeployment of WebRTC gateways 104 and WebRTC compliant devices andapplications.

FIG. 4 depicts an illustrative embodiment of a first communicationsystem 400 for delivering media content. The communication system 400can represent an Internet Protocol Television (IPTV) media system.Communication system 400 can be overlaid or operably coupled with system100 of FIG. 1 as another representative embodiment of communicationsystem 400. Some of the devices depicted in communication system 400 canbe configured to use portions of method 300 to enable WebRTCapplications with non-WebRTC compliant legacy devices.

The IPTV media system can include a super head-end office (SHO) 410 withat least one super headend office server (SHS) 411 which receives mediacontent from satellite and/or terrestrial communication systems. In thepresent context, media content can represent, for example, audiocontent, moving image content such as 2D or 3D videos, video games,virtual reality content, still image content, and combinations thereof.The SHS server 411 can forward packets associated with the media contentto one or more video head-end servers (VHS) 414 via a network of videohead-end offices (VHO) 412 according to a multicast communicationprotocol.

The VHS 414 can distribute multimedia broadcast content via an accessnetwork 418 to commercial and/or residential buildings 402 housing agateway 404 (such as a residential or commercial gateway). The accessnetwork 418 can represent a group of digital subscriber line accessmultiplexers (DSLAMs) located in a central office or a service areainterface that provide broadband services over fiber optical links orcopper twisted pairs 419 to buildings 402. The gateway 404 can usecommunication technology to distribute broadcast signals to mediaprocessors 406 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 408 such as computers or televisionsets managed in some instances by a media controller 407 (such as aninfrared or RF remote controller).

The gateway 404, the media processors 406, and media devices 408 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth, Zigbee, or other present ornext generation local or personal area wireless network technologies. Byway of these interfaces, unicast communications can also be invokedbetween the media processors 406 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 429 can be used in the mediasystem of FIG. 4. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 400. In thisembodiment, signals transmitted by a satellite 415 that include mediacontent can be received by a satellite dish receiver 431 coupled to thebuilding 402. Modulated signals received by the satellite dish receiver431 can be transferred to the media processors 406 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 408. The media processors 406 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 432 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 433 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system400. In this embodiment, the cable TV system 433 can also provideInternet, telephony, and interactive media services.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 430, a portion of which can operate as aweb server for providing web portal services over the ISP network 432 towireline media devices 408 or wireless communication devices 416.

Communication system 400 can also provide for all or a portion of thecomputing devices 430 to function as a service translation gateway(herein referred to as service translation gateway 430). Similarly,communication system 400 can also provide for all or a portion of thecomputing devices 435 to function as a WebRTC gateway (herein referredto as WebRTC gateway 435). The service translation gateway 430 and theWebRTC gateway 435 can use computing and communication technology toperform functions 462 and 463, respectively, which can include amongother things, the functions described in method 300 of FIG. 3. The mediaprocessors 406 and wireless communication devices 416 can be provisionedwith software functions 462 and 466, respectively, to utilize theservices of the service translation gateway 430 and the WebRTC gateway435.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 417 operating according to common wireless access protocolssuch as Global System for Mobile Communications or GSM, Code DivisionMultiple Access or CDMA, Time Division Multiple Access or TDMA,Universal Mobile Telecommunications System or UMTS, Worldwideinteroperability for Microwave Access or WiMAX, Software Defined Radioor SDR, Long Term Evolution or LTE, LTE Advanced or LTE-A, and so on.Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 5 depicts an illustrative embodiment of a communication system 500employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 500 can be overlaid or operably coupledwith system 100 of FIG. 1 and communication system 400 as anotherrepresentative embodiment of communication system 400. Some of thedevices depicted in communication system 400 can be configured to useportions of method 300 to enable WebRTC applications with non-WebRTCcompliant legacy devices.

Communication system 500 can comprise a Home Subscriber Server (HSS)540, a tElephone NUmber Mapping (ENUM) server 530, and other networkelements of an IMS network 550. The IMS network 550 can establishcommunications between IMS-compliant communication devices (CDs) 501,502, Public Switched Telephone Network (PSTN) CDs 503, 505, andcombinations thereof by way of a Media Gateway Control Function (MGCF)520 coupled to a PSTN network 560. The MGCF 520 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 520.

IMS CDs 501, 502 can register with the IMS network 550 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 540. To initiate acommunication session between CDs, an originating IMS CD 501 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 504 which communicates with a corresponding originating S-CSCF506. The originating S-CSCF 506 can submit the SIP INVITE message to oneor more application servers (ASs) 517 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 517 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 506 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 506 can submit queries to the ENUMsystem 530 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 507 to submit a query to the HSS 540 toidentify a terminating S-CSCF 514 associated with a terminating IMS CDsuch as reference 502. Once identified, the I-CSCF 507 can submit theSIP INVITE message to the terminating S-CSCF 514. The terminating S-CSCF514 can then identify a terminating P-CSCF 516 associated with theterminating CD 502. The P-CSCF 516 may then signal the CD 502 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 5 may be interchangeable. It is further noted that communicationsystem 500 can be adapted to support video conferencing. In addition,communication system 500 can be adapted to provide the IMS CDs 501, 502with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PSTN CD such as CD503 or CD 505 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 530 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 506 to forward the call to the MGCF 520 via a Breakout GatewayControl Function (BGCF) 519. The MGCF 520 can then initiate the call tothe terminating PSTN CD over the PSTN network 560 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 5 can operate as wirelineor wireless devices. For example, the CDs of FIG. 5 can becommunicatively coupled to a cellular base station 521, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 550 of FIG. 5. The cellular accessbase station 521 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 5.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 521 may communicate directly with the IMS network 550 as shownby the arrow connecting the cellular base station 521 and the P-CSCF516.

It is further understood that alternative forms of a CSCF can operate ina device, system, component, or other form of centralized or distributedhardware and/or software. Indeed, a respective CSCF may be embodied as arespective CSCF system having one or more computers or servers, eithercentralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respective CSCF.Likewise, other functions, servers and computers described herein,including but not limited to, the HSS, the ENUM server, the BGCF, andthe MGCF, can be embodied in a respective system having one or morecomputers or servers, either centralized or distributed, where eachcomputer or server may be configured to perform or provide, in whole orin part, any method, step, or functionality described herein inaccordance with a respective function, server, or computer.

The service translation gateway 430 and the WebRTC gateway 435 of FIG. 4can be operably coupled to the second communication system 500 forpurposes similar to those described above. The service translationgateway 430 and the WebRTC gateway 435 can perform function 462 and 463,respectively, and thereby enable the CDs 501, 502, 503 and 505 of FIG. 5to access to services provided by legacy non-WebRTC network resources asdescribed earlier. CDs 501, 502, 503 and 505, which can be adapted withsoftware to perform function 572 to utilize the services of the servicetranslation gateway 430 and the WebRTC gateway 435. In one embodimentthe service translation gateway 430 and/or the WebRTC gateway 435 can bean integral part of the application server(s) 517 performing function574 or 575, which can be substantially similar to functions 462 and 462,respectively, and adapted to the operations of the IMS network 550.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as ^(3rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 6 depicts an illustrative embodiment of a web portal 602 which canbe hosted by server applications operating from the computing devices430 of the communication system 100 illustrated in FIG. 1. Communicationsystem 600 can be communicatively coupled with system 100, communication400, and/or communication system 500. The web portal 602 can be used formanaging services of system 100 and communication systems 400-500. A webpage of the web portal 602 can be accessed by a Uniform Resource Locator(URL) with an Internet browser such as Microsoft's Internet Explorer™,Mozilla's Firefox™, Apple's Safari™, or Google's Chrome™ using anInternet-capable communication device such as those described in FIGS.1-2. The web portal 602 can be configured, for example, to access amedia processor 106 and services managed thereby such as a Digital VideoRecorder (DVR), a Video on Demand (VoD) catalog, an ElectronicProgramming Guide (EPG), or a personal catalog (such as personal videos,pictures, audio recordings, etc.) stored at the media processor 106. Theweb portal 602 can also be used for provisioning IMS services describedearlier, provisioning Internet services, provisioning cellular phoneservices, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 462-466, and 572-575 to adapt these applicationsas may be desired by subscribers and service providers of system 100 andcommunication systems 400-500.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and 4-5.Communication device 700 in whole or in part can represent any of thecommunication devices described in FIGS. 1 and 4-5 and can be configuredto perform portions of method 300 of FIG. 3.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth, ZigBee, WiFi, DECT, orcellular communication technologies, just to mention a few. Cellulartechnologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS,TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generationwireless communication technologies as they arise. The transceiver 702can also be adapted to support circuit-switched wireline accesstechnologies (such as PSTN), packet-switched wireline accesstechnologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 400 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 400.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 400 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofthe media processor 406, the media devices 408, or the portablecommunication devices 416 of FIG. 4, as well as the IMS CDs 501-502 andPSTN CDs 503-505 of FIG. 5. It will be appreciated that thecommunication device 700 can also represent other devices that canoperate in communication systems 400-500 of FIGS. 4-5 such as a gamingconsole and a media player.

The communication device 700 shown in FIG. 7 or portions thereof canserve as a representation of one or more of the devices of system 100 ofFIG. 1, communication system 400, and communication system 500. Inaddition, the controller 706 can be adapted in various embodiments toperform the functions 462-466 and 572-575, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, referring to FIG. 2, in oneembodiment, the service translation gateway 106 can utilize the HLLAPI,LLAPI, and markup language elements for generating a WebRTCsingle-system image within a plurality of distributed, heterogeneouscomputing platform and runtime environments.

In another embodiment, HLLAPI used by the service translation gateway106 can define a distributed, system-independent structured protocolboundary across which markup language requests, unstructured datasets,structured datasets, replies, error messages, and completion codes aresent and received.

In another embodiment, a plurality of HLLAPIs used by the servicetranslation gateway 106 can be incorporated into the markup language.

In another embodiment, LLAPI used by the service translation gateway 106can define a system-dependent structured protocol boundary across whichmarkup language requests, unstructured datasets, structured datasets,replies, error messages, and completion codes are sent and received.

In another embodiment, a plurality of LLAPIs used by the servicetranslation gateway 106 can be incorporated into the markup language.

In another embodiment, a plurality of standalone, system-dependentmarkup language LLAPI tags can be registered and cached toheterogeneous, distributed WebRTC runtime platforms and networkcomputing environments.

In another embodiment, a plurality of WebRTC applications, processes anddevices can access the service translation gateway 106 utilizing aplurality of markup language, HLLAPI, and LLAPI elements.

In another embodiment, the markup language used by the servicetranslation gateway 106 can incorporate system-independent API operationsyntactic tag elements, including <webrtcmetaapi>, <webrtcapitransform>,<webrtchllapi>, <webrtcllapi>, <webrtcgetUserMedia>,<webrtcPeerConnection>, <webrtcDataChannels>.

In another embodiment, the markup language used by the servicetranslation gateway 106 can incorporate system-independent mathematicaloperation syntactic tag elements, including <webrtcvector>,<webrtcscalar>, <webrtcmatrixalgebra>, <webrtclinearalgebra>,<webrtcdiffcalculus>, <webrtcgeometry>, <webrtctrig>.

In another embodiment, the markup language used by the servicetranslation gateway 106 can incorporate system-independent Boolean logicoperation syntactic tag elements, including <webrtcAND>, <webrtcOR>,<webrtcNOT>, <webrtcNAND>, <webrtcNOR>, <webrtcXOR>, <webrtcXNOR>.

In another embodiment, the markup language used by the servicetranslation gateway 106 can incorporate system-independent syntactic tagelements, including <webrtctext>, <webrtcfile>, <webrtcvoice>,<webrtcvideo>, <webrtcimage>, <webrtcvector>, <webrtcscalar>,<webrtcgenericobject>, <webrtcmathfn>, <webrtcalgorithm>, <webrtcgps>,<webrtcgis>, <webrtchtml>, <webrtcmetadata>, <webrtcsecurity>,<webrtcsynch>, <webrtcasynch>.

In another embodiment, the service translation gateway 106, HLLAPI,LLAPI, and markup language elements are power- and performance-optimizedto a plurality of heterogeneous mobile devices and mobile applications.

In another embodiment, the service translation gateway 106, HLLAPI,LLAPI, and markup language elements function both with network presenceand with no network presence.

In another embodiment, markup language elements used by the servicetranslation gateway 106 can perform deep packet inspection (DPI) ofmarkup language-tagged data.

In another embodiment, the service translation gateway 106, HLLAPI,LLAPI, and markup language elements are power- and performance-optimizedto a plurality of Daytona, NELOS, Carrier IQ, Detractors, Mark the Spot,CDR, Tickets, Alarms, Boundary, RAN Feed, Network Stats, Network Config,Femtocell, Microcell, Capital Planning, MTi Incident, and Wi-Fi mobile,heterogeneous, distributed processing platforms and runtimeenvironments.

In another embodiment, the service translation gateway 106, HLLAPI andLLAPI elements interface with a plurality of standalone and distributed,heterogeneous WebRTC computing environments.

Other embodiments can be used in the subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods describe above. One or more instances of the machine canoperate, for example, as the WebRTC gateway 104, 435, the servicetranslation gateway 106, 430 and other devices of FIGS. 1, and 4-5. Insome embodiments, the machine may be connected (e.g., using a network826) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine inserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU), a graphics processing unit (GPU,or both), a main memory 804 and a static memory 806, which communicatewith each other via a bus 808. The computer system 800 may furtherinclude a display unit 810 (e.g., a liquid crystal display (LCD), a flatpanel, or a solid state display. The computer system 800 may include aninput device 812 (e.g., a keyboard), a cursor control device 814 (e.g.,a mouse), a disk drive unit 816, a signal generation device 818 (e.g., aspeaker or remote control) and a network interface device 820. Indistributed environments, the embodiments described in the subjectdisclosure can be adapted to utilize multiple display units 810controlled by two or more computer systems 800. In this configuration,presentations described by the subject disclosure may in part be shownin a first of the display units 810, while the remaining portion ispresented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices that can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) can include, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. It is furthernoted that a computing device such as a processor, a controller, a statemachine or other suitable device for executing instructions to performoperations or methods may perform such operations directly or indirectlyby way of one or more intermediate devices directed by the computingdevice.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP, HTTPS) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth, WiFi, Zigbee), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE, LTE-A) can beused by computer system 800.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are also merely representationaland may not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,can be used in the subject disclosure. In one or more embodiments,features that are positively recited can also be excluded from theembodiment with or without replacement by another component or step. Thesteps or functions described with respect to the exemplary processes ormethods can be performed in any order. The steps or functions describedwith respect to the exemplary processes or methods can be performedalone or in combination with other steps or functions (from otherembodiments or steps that have not been described).

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more steps or functions, where thefacilitating can include less than all of the steps needed to performthe function or can include all of the steps of function, such asfacilitating access or facilitating establishing a connection.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A method, comprising: receiving, by a webreal-time communications gateway comprising a processor, a first requestfrom a mobile communication device identifying communication servicesrequested from a network resource that does not utilize a web real-timecommunications protocol used by the web real-time communicationsgateway, wherein the first request is compliant with the web real-timecommunications protocol; generating, by the web real-time communicationsgateway, a second request comprising a markup language that differs fromthe web real-time communications protocol, wherein the markup languageis used by a service translation gateway that interfaces the webreal-time communications gateway to a plurality of network resourcesthat do not conform to the web real-time communications protocol, andwherein the plurality of network resources includes the network resourceidentified in the first request; transmitting, by the web real-timecommunications gateway, the second request to the service translationgateway to cause the service translation gateway to facilitate thecommunication services of the network resource identified in the firstrequest; receiving, by the web real-time communications gateway, a firstmessage from the mobile communication device, wherein the first messageis compliant with the web real-time communications protocol used by theweb real-time communications gateway; translating, by the web real-timecommunications gateway, the first message to a first updated messageconforming to the markup language used by the service translationgateway; and transmitting, by the web real-time communications gateway,the updated first message to the service translation gateway fordelivery to the network resource facilitating the communication servicesidentified in the first request.
 2. The method of claim 1, furthercomprising receiving, by the web real-time communications gateway, asecond updated message from the service translation gateway, wherein thesecond updated message is compliant with the markup language, andwherein the second updated message is generated by the servicetranslation gateway responsive to translating a second message providedto the service translation gateway by the network resource while thenetwork resource facilitates the communication services identified inthe first request.
 3. The method of claim 2, further comprisingtranslating, by the web real-time communications gateway, the secondupdated message to a third message compliant with the web real-timecommunications protocol for delivery to the mobile communication device.4. The method of claim 1, wherein a portion of the first message isdirected to a second communication device by way of the web real-timecommunications gateway, the service translation gateway, and the networkresource facilitating the communication services identified in the firstrequest.
 5. The method of claim 1, wherein a protocol used forcommunications between the service translation gateway and the networkresource differs from the markup language used between the web real-timecommunications gateway and the service translation gateway.
 6. Themethod of claim 1, wherein the network resource comprises a shortmessage service server that does not utilize the web real-timecommunications protocol.
 7. The method of claim 1, wherein the networkresource comprises a multimedia messaging service server that does notutilize the web real-time communications protocol.
 8. The method ofclaim 1, wherein the web real-time communication protocol is promulgatedby in whole or in part by a world wide web consortium, an internetengineering task force group, or a combination thereof.
 9. The method ofclaim 1, wherein the markup language comprises a high-level applicationprogramming interface, and a low-level application programminginterface.
 10. The method of claim 9, wherein the high-level applicationprogramming interface is utilized to improve a performance ofcommunications between the web real-time communications gateway and theservice translation gateway.
 11. The method of claim 9, wherein thelow-level application programming interface is utilized to improve aperformance of computing resources used by the web real-timecommunications gateway or the service translation gateway.
 12. Amachine-readable storage medium, comprising executable instructions,wherein execution of the instructions by a processor, causes theprocessor to perform operations comprising: receiving a first requestfrom a communication device requesting communication services from anetwork resource that does not utilize a web real-time communicationsprotocol, wherein the first request is compliant with the web real-timecommunications protocol; generating a second request comprising a markuplanguage that differs from the web real-time communications protocol,wherein the markup language is used by a service translation gatewaythat interfaces to a plurality of network resources that do not utilizethe web real-time communications protocol, and wherein the plurality ofnetwork resources includes the network resource identified in the firstrequest; transmitting the second request to the service translationgateway to facilitate the communication services of the network resourceidentified in the first request; receiving a first message from thecommunication device, wherein the first message is compliant with theweb real-time communications protocol; translating the first message toa first updated message conforming to the markup language used by theservice translation gateway; and transmitting the updated first messageto the service translation gateway for delivery to the network resourcefacilitating the communication services identified in the first request.13. The machine-readable storage medium of claim 12, wherein theoperations further comprise receiving a second updated message from theservice translation gateway, wherein the second updated message iscompliant with the markup language, and wherein the second updatedmessage is generated by the service translation gateway responsive totranslating a second message provided to the service translation gatewayby the network resource.
 14. The machine-readable storage medium ofclaim 13, wherein the operations further comprise translating the secondupdated message to a third message compliant with the web real-timecommunications protocol for delivery to the communication device. 15.The machine-readable storage medium of claim 12, wherein a portion ofthe first message is directed to a second communication device by way ofthe service translation gateway and the network resource facilitatingthe communication services identified in the first request.
 16. Themachine-readable storage medium of claim 12, wherein a protocol used forcommunications between the service translation gateway and the networkresource differs from the markup language.
 17. The machine-readablestorage medium of claim 12, wherein the network resource comprises ashort message service server or a multimedia messaging service serverthat does not utilize the web real-time communications protocol, andwherein the web real-time communication protocol is promulgated by inwhole or in part by a world wide web consortium, an internet engineeringtask force group, or a combination thereof.
 18. A service translationgateway, comprising: a memory to store executable instructions; and aprocessor coupled to the memory, wherein execution of the instructionsby the processor, causes the processor to perform operations comprising:receiving from a web real-time communications gateway a first requestfor communication services from a network resource, wherein thecommunication services are requested by a communication devicecommunicatively coupled to the web real-time communications gateway,wherein the network resource does not utilize a web real-timecommunications protocol used by the web real-time communicationsgateway, and wherein the first request is compliant with a markuplanguage that differs from the web real-time communications protocol;directing the network resource to provide the communication servicesidentified in the first request; receiving a first message from the webreal-time communications gateway, wherein the first message is compliantwith the markup language; translating the first message to a firstupdated message conforming to a protocol used by the network resource,wherein protocol differs from the markup language used for communicatingwith the web real-time communications gateway; and transmitting theupdated first message to the network resource facilitating thecommunication services identified in the first request.
 19. The servicetranslation gateway of claim 18, wherein the operations furthercomprise: receiving a second message from the network resource, whereinthe second message is compliant with the protocol used by the networkresource; translating the second message to an updated second messageconforming to the markup language; and transmitting the updated secondmessage to the web real-time communications gateway for delivery to thecommunication device after the web real-time communications gatewaytranslates the updated second message to a third message compliant withthe web real-time communications protocol.
 20. The service translationgateway of claim 18, wherein a portion of the first message is directedto a second communication device by way of the network resource.